## Summary

Adds `trueblocks` as an `additional_services` option that runs
[chifra](https://github.com/TrueBlocks/trueblocks-core) daemon — the
TrueBlocks REST API — against a participant EL on container port 8080.
Per-chain `trueBlocks.toml` is rendered for the active network
(`network_params.network` / `network_id`), and `allocs.csv` is
pre-staged for unknown chains so `chifra`'s archive check passes. Image
is published from
[ethpandaops/eth-client-docker-image-builder#384](ethpandaops/eth-client-docker-image-builder#384).

The package runs `chifra daemon` only. The scraper isn't started
automatically — POST `/scrape` on the daemon (or run `chifra scrape`
against the same data dir) when you want to build the local [Unchained
Index](https://trueblocks.io/docs/install/get-the-index/). The other
chifra endpoints (`/status`, `/blocks`, `/receipts`, `/transactions`,
`/traces`, `/logs`) work without an index — they're chifra-flavored RPC
pass-through.

## Configuration

```yaml
trueblocks_params:
  image: "ethpandaops/trueblocks:v5.9.3"
  # Verbatim RPC URL chifra should target. Leave empty to use
  # all_el_contexts[target_index] (the in-cluster participant).
  target_rpc_url: ""
  target_index: 0
  scrape:                # written into trueBlocks.toml; 0 = network-aware default
    apps_per_chunk: 0
    snap_to_grid: 0
    first_snap: 0
    unripe_dist: 0
  env: {}
```

Devnet example:

```yaml
participants:
  - el_type: erigon
    cl_type: lighthouse
additional_services:
  - trueblocks
```

## Notes

`chifra`'s `IsNodeArchive` does a CSV-vs-RPC consistency check rather
than a real archive probe, so it returns `false` on chains we don't ship
a bundled `allocs.csv` for. The launcher works around it by writing a
self-consistent `allocs.csv` for the active chain in a one-shot
`plan.run_sh` bootstrap (probes the first prefund's actual block-0
balance, drops the rendered toml in alongside the image's bundled
per-chain configs, stores the result as a files artifact mounted into
the daemon container). Filed upstream:
[TrueBlocks/trueblocks-core#4044](TrueBlocks/trueblocks-core#4044).

We considered khedra (the official `chifra daemon` + `chifra scrape`
unified successor) but its startup `Configured()` check requires a
reachable mainnet RPC returning chainId 1, which doesn't fit hermetic
devnets. Filed upstream:
[TrueBlocks/trueblocks-khedra#22](TrueBlocks/trueblocks-khedra#22)
— if a headless mode lands, we can migrate.

## Test plan

- [x] Erigon + Lighthouse devnet: daemon comes up healthy, `/status`
returns `isArchive: true, isTracing: true, trueblocksVersion:
GHC-TrueBlocks//5.9.3`; `/blocks?blocks=0` returns genesis;
`/list?addrs=<prefund>` returns appearances after a `POST /scrape`;
`/chunks?mode=index` reflects the new chunk.
- [x] bal-devnet-7 client images (Erigon + Reth × Lighthouse + Lodestar
matrix, fulu @ 0, gloas @ 9): same checks pass against chifra v5.9.3 +
erigon 3.5.0.
- [x] `kurtosis lint --format` clean; `kurtosis run --dry-run` clean.